Apparently, the task scheduler in all Windows NT-derived versions up to (and including) Windows Server 2003 cannot run jobs under the "NT Authority\Network Service" security principal; "NT Authority\System" is the only so-called well-know security principal that can be used with it. Support for running tasks as "Network Service" or "Local Service" was only added in Task Scheduler 2.0, which is the version that ships with Vista and will be also included in Windows Server 2008.

Side note: I wonder why the link above, being a command reference for an administrative tool, is on the MSDN and not on the Technet site.

Practical implication is that without being able to use the "Network Service" principal, a distinct network account (domain account or server account) is required for any job that needs to access any network resource. This also means keeping track of another account and password — and taking care of controlling and auditing it's access; whereas the "Network Service" principal cannot normally be used for interactive sessions.

Annoyingly, the task scheduler UI also does not tell you that you can't if you try, but rather gives the un-helpful message "Access is denied. You do not have permission to perform the requested operation".
The same message is also shown when, for a regular account, the password entered does not match the actual account password. (This happened to me because the keyboard layout on a remote desktop session turned out to be not what I thought it was)
Anyone know if the error reporting has improved anything in the new task scheduler?

Wouter, I wonder why you didn't just rsync the whole filesystem over and used it as a chroot, while gradually rolling over services to the actual new system?

So Sun has snapped up MySQL. Thinking about the express editions of their SQL database offerings Microsoft, IBM and Oracle released a few years back, to compete with MySQL, I wonder how nervous this news makes them.

I also wonder whether Sun would start offering a default MySQL installation option on their servers. This could make for some more nervosity. Especially if they do it also for their Windows servers...

Still no solution on the issues I wrote about a few days ago.
Mentions of the problems are surprisingly few and in between; either it's not universal or people just don't notice / are not bothered by it.

Something awry on Gmail this evening... I've been having status messages — you know, the yellow/orangish overlay on top of the page that usually shows when an action has finished — telling me that "the system encountered a problem" for a few hours now while reading my email, intermittently.
Now all of a sudden, I'm dropped in the "old version" of the Gmail interface and there's no longer a choice at the top for the current UI, you know, the one with the funky coloured labels and such; which disappearance leads me to believe that it's not just a client side issue. I'm simply curious now how long it'll take them to fix things.

*Update* As I finished this post and went back to navigating through Gmail, the new UI is back. That didn't take them long...
*Second update* ... but the service also wasn't fixed, I almost immediately started getting error status messages again. And now I'm back into the "old" UI. As I'll be off for bed soon, I probably won't find out how long it'll take. Not that I'm that interested.

Yesterday I noticed two particular headlines standing out in the financial news. The oldest, which was actually from tuesday, read that the European Central Bank was again injecting money into the financial markets. The other one was that home confiscations in the US were way up.

I think the ECB is sending a very bad message to financial institutions here, not by intervening in the market in the first place, but by continuing to provide shelter after a couple of weeks: “act however irresponsibly that you wish to, we'll help you out if you get into trouble anyway.”

While they bear a large part of the responsibility by financing the US mortgage crisis in the first place, big institutions will get out largely unharmed in the long run. At the same time real persons — often lured by overly bullish financial news undoubtedly — will get burned, together with some of the smaller lenders who cannot get enough money back in time.

Capitalist protectionism, at its worst.

Last monday I had to order a computer for use as a workstation for a graphic designer. When I called Dell and asked for a specification on a Dimension system, the — overall very helpful and friendly — account manager stated that the Dimension range was discontinued for business customers and available for consumers only. He told me that the new Vostro line was their new SMB offer.

When I pointed out to him that not only was the Dimension still listed on their SMB web pages, but that the Vostro was inattractive because it could not be upgraded beyond 4GB of memory, he was surprised at first and then stated that a 64 bit OS was needed anyway to be able to use more than 4GB of memory'.
But if I needed more memory, a Precision workstation would be a good alternative. Well, any Precision I could configure on the Dell website would end up costing 1.5 times as much as a similarly configured Dimension. (which means that I had to add a graphics card with higher 3D performance on the Dimension as what was needed, since this computer was meant for 2D graphic design)
At this point, the sales representative tried building a Precision configuration himself to specifications I had provided him with, but with maximum discount he could apply the price still came out over 30% (meaning, over 300 EUR) more than a Dimension to these same specs. At which point he gave in :)

I seriously hope that the sales person was mistakenly saying that the Dimension would go away as a Dell business offer (though that means that some review of internal communications would be in order). While I'm sure the Vostro line has it's merit, these are some points that make it a lousy or at least undesirable option in some cases:

• memory size limited to 4GB
• currently, no quad core processor option — while this may not be very benificial a lot of the time it would improve workloads that can make use of threading; in addition the Q6600 on the Dimension was only about 10 EUR more costly than the dual core E6600
• while it wasn't that much of an issue in this case, the actual lack of an option to configure a better 3D graphics card than the preconfigured card

The way I see it, the Vostro should be a valuable add-on to Dell's SMB offering at the bottom segment. Throwing out the Dimension would leave a hole between Vostro and Precision. And I'm not sure where exactly the Optiplex fits in; it appears to be more along the Vostro looking at specs, but it's price tag is closer to Precision — it's main feature seems to be a highr default support level.

Well, I don't know John Brougher well enough to judge his wisdom, but today I read Slow down the queuing and it was so recognizable. Especially the symptoms of bookmark queuing and tabbed browser sessions.

And, independently, (mainly guided by tips from a number of other "personal improvement" blogs) I had come to the same resolution of the problem. So there must be wisdom at least in his article...

A month or two ago, I installed Etch/amd64 on a HP system which uses the ATI SB400 chipset. It worked great mostly, but sound was choppy from the start.
I decided this week to investigate and quickly discovered that oss emulation on this chipset is giving most people issues. It turns out the solution, for a GNOME desktop, is really simple: remove the libesd0 package and install libesd-alsa0 instead, so that esd does not use OSS emulation.

Which begs the question, could the Debian installation system be made smarter so that systems using ALSA drivers wouldn't use OSS unless for applications that only support the latter?

Today I discovered a very useful and nearly undocumented Openswan configuration parameter, which goes by the name of leftsourceip (and symmetrically rightsourceip). What it does is telling the Linux Openswan VPN gateway what address to send traffic from, which it generates itself, and is destined for the other side of the VPN connection. Apparently there are some caveats when using the KLIPS IPsec stack, but it works great when using NETKEY. Details available in the thread up to and following this message on the Openswan Users mailinglist.

The immediate advantage of using leftsourceip is that you can just reach machines on the far end of the connection, from either gateway where you've set it, without having to specify source interface or address on the internal network.

There's already a patch in the Openswan BTS; hopefully it will be integrated soon.

The picture below is a hardware test setup I ran this morning, with an old and discarded motherboard which has a Pentium III CPU on it running at 733 MHz. Since that's still faster than any other system I own save for the ibook (which is a G3 running at 800 MHz), I wanted to see if it was truely broken as reported, or not. The issue, which I actually witnessed before, was that on initial boot it tended to restart up, to a few dozen times. These restarts could happen from early post BIOS stage up to while logging on. Once it had been powered on for a little while, the restarts would usually go away.



I assembled any missing parts - video card, memory, and an AT case from which I used the reset button as the power switch to the ATX motherboard - and started by running memtest on it. Which ran just fine for nearly half an hour; but I ran memtest before to try and help diagnose the problem and it had run fine then, too.
So I crossed my fingers and tried running a Linux Live CD from it. Unfortunately, after about half a minute the system restarted once again. The only parts remaining from the original system were the motherboard and CPU, power supply and DVD-ROM (but not the IDE cable). With that in mind, the most likely culprits are indeed motherboard or CPU.

Chances of being able to rescue the parts are nearly nil, but I'm still curious about what could be the actual failing part. Are there any thorough hardware tests around, which could be run (preferably) from bootable CD or floppy?

While I did not aim for it, it was a little disappointing to learn that I got soooooo close to hitting #350000.

Not sure that I have enough of it, but I can try anyway. Here's one for the unlucky administrators who have an Exchange server amidst their server farm.
If a windows server running Exchange 2003 logs the following error event in the System log when it is restarted:

Access denied attempting to launch a DCOM Server. The server is:
 9DA0E106-86CE-11D1-8699-00C04FB98036 
The user is SYSTEM/NT AUTHORITY, SID=S-1-5-18.

then one possible cause is that the Microsoft Search service is missing a startup dependency on the Exchange Information Store – which is not obvious from anything in the event message or the surrounding ones. Searching the web does not list anything relevant at first either, you have to check lower ranked results to find the solution listed in the post by user "zeeshan_xt" in this message board thread. Hopefully this post helps it move up a bit.

Last evening when I left work it was snowing but only lightly, what fell did not really stay lying on the roads. I decided it was safe enough to still drive home by motorcycle.

A few kilometres further, suddenly thick flakes started falling out and soon I had to open up my wind shield because I could not keep up wiping it my hand to remove the snow that stuck on it. Off course, even at 30 km/h it is not exactly funny to get icy snowflakes into your eyes. What was worse, by the time the snow started falling seriously I had gotten onto the highway and I could not immediately turn around or get off.

Since it was snowing steadily and heavily, a several cm thick carpet started building. After another few kilometres I had to pull aside because I could no longer keep my bike on track and I called for an uncle who owns a van to come and pick me up. So he did; when we drove off it turned out that only one or two kilometres further along the road it had hardly been snowing and a carpet had not started building up yet.

To make up for the annoyance of yesterday evening, this morning the sky looks beautiful.

Filip complained that the unofficial sarge amd64 jigdo files didn't work for him. That's fine. But if you want other people to notice the bug and fix please report it properly! In this case, I spotted his blog post and investigated. I think I've fixed the problem now Filip...

Trying to build the unofficial Sarge DVD images for AMD64 today, jigdo-lite could not find several packages on the regular mirrors. Next it tried to fallback to amd64-cdsnap.debian.net, which I believe is a mirror listed in the jigdo template, but still failed to find them over there. Browsing the port pages, I found out that the Sarge release for amd64 is hosted on amd64.debian.net rather than that -cdsnap location. It seems those jigdo templates need an update...

Ok, so I have my Mac Mini ready to overtake my old PC as my home server/gateway/whatnot. Before anything, I must thank Filip for his warning - I had left 3GB at the end of the disk to set up MacOS - Just for fun, just to play with it, maybe even to use the Mac On Linux trick. Anyway, if I want to do anything with MacOS, I can use Nadezhda's G5 imac... And it is not sane to have a server's interface to the world rely on a stack of two (cooperating, but still...) OSs. I'll just stick to good ol' wired Ethernet.
PS: Fuck Broadcom.

It so happened that my ibook had a 8GiB free space area at the end of the hard drive, and therefore I decided to wanted to use that for MacOS X instead of the 2GiB partition that was used for it before. Trying to avoid problems with bad partitions, I booted from the OSX installation/rescue CD and opened Disk Utility.

To play safe, I locked the existing OSX partition for editing and then assigned the 8GiB free space area to a new hfs+ partition. When I committed, suddenly the existing partition label went blank. WTF??? Had Disk Utility decided it should format what that partition as well? Great, now I'd have to reinstall anyway instead of copying things over.

I rebooted to check partition numbers in linux, but instead of the yaboot prompt I got an alternating question mark / happy face, and after a couple of seconds it booted from the rescue CD again which was still in there. Apparently my bootstrap partition got messed with too. Not funny.

I powered off and inserted a bootable linux CD to chroot into the existing system and rerun ybin. However when I tried to mount the linux root partition it would not want to do so. I checked the partition numbers with fdisk and suddenly my stomach felt like it was tied into a knot: instead of using only the free space as told, Disk Utility had wiped the entire drive and created a 2GiB partition at the beginning and assigned the remaining 28GiB to the new partition instead.

So now I'm left with a ibook shaped paperweight for the time being. Luckily I did not keep anything really important on the laptop, but I did lose some uncommitted programming work, and some of my wife's old mail. Not to mention the time I'll lose by being unable to use it the first few days and having to reinstall it instead. So people: never trust a tool tailored for dummies to something as important as disk partitioning. And to Apple: FIX THE FUCKING PROGRAM SO IT DOES AS IS IT TOLD TO DO AND NOTHING ELSE!